Description:
JavaServer hangs when requesting service from a DNS server that is offline. This is due to a bug in all versions of the Solaris Green Threads Virtual Machine.Workaround:The symptoms of this bug are that the server does not respond to connections and a thread stack dump of the server (achieved by sending SIGQUIT to the Virtual Machine process) shows one or more threads hung in
InetAddress.getHostName()
.
Log with client IP addresses, not their hostnames.
There are several properties that are specific to servers that cannot be viewed or changed in the admin UI.Workaround:
Edit the property files by hand.
Listing of very large realms can be slow in the security section.Workaround:
Avoid large realms.
The Help buttons bring up a secondary browser window to show the help pages.Workaround:There are two main problems with this:
- The help window obscures the applet window, making it unclear that the help is actually showing in a separate window.
- The Back button on the browser can return to the applet page, causing users to think they need to sign on again, resulting in two or more sessions at once.
Move the help window when it first comes up. Don't iconify the help window, and don't click the browser's Back button in the help window.
Some properties cannot be managed from the admin applet. Currently these fields include:Workaround:
- Unix user/group to run as
- DNS name resolution in logging
- Rolling in roll files turned on or off
- Enable/disable servlet URL loading
Edit the property files by hand.
Unix shutdown will not gracefully shutdown the server. We should provide a commandline utility that will shutdown the server if run as root.Workaround:
Use operating system commands to stop the server.